-
Notifications
You must be signed in to change notification settings - Fork 4.6k
HLT menu development for 12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X]
#38482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HLT menu development for 12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X]
#38482
Conversation
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38482/30703
|
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@Martin-Grunewald, @jordan-martins, @AdrianoDee, @bbilin, @cmsbuild, @missirol, @srimanob, @kskovpen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
enable gpu |
|
please test |
CMSSW_12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X]12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X]
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-865996/25736/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
|
I noticed that |
|
Yes, it should be added under 'frozen' together with the Fake* in these PRs. |
|
... and also under 'all' |
In runOne, "frozen" does not include the Fake menus (those are only under "fake"). I assume we want to keep the same structure ("frozen"=frozenGRun, "fake"=fake menus). |
|
Ah yes, fake for the fakes, frozen for the real non-fake menus such as 2022v12!! |
…1.2 for 2022 (branch: 12_5_X)
7d1b9f3 to
443361e
Compare
|
+hlt
|
|
@cms-sw/pdmv-l2 @cms-sw/upgrade-l2 , please consider reviewing this PR and its backport. The latter is needed for the upcoming MC production in The changes in |
|
I think I understand now the differences in This PR modifies the In the wfs in question, this modifies the output of "step2", which is the input to "step3". The histograms in questions are filled in "step3" by the Validation plugin
This can explain the differences (more entries in those HCAL plots post-PR, because the EDM input contains more collections of HCAL RecHits). I dare say that HLT makes no guarantee that the collections in |
|
+Upgrade From the upgrade side, only HLT key is updated from 2021 to 2022. |
|
urgent |
|
@cms-sw/pdmv-l2 , a second ping to review this PR (and its backport). The only change to review is the renaming of We should start testing these PRs in IBs asap, to exclude unexpected issues in time for the next |
|
+pdmv |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
|
Sorry - just did! |
|
+1 |
PR description:
CMSSW_12_4_X.CMSSW_12_4_0.V1.2frozen (GRun) menu to be used for MC production in12_4_X.This is the PR for the
masterbranch, which will then be backported to12_4_X(the latter is the release cycle currently used for HLT-menu development for Run 3).Includes the integration of the following JIRA tickets.
HLTDebug*EventContents withDQMGPUvsCPUoutput collectionsHLT_Mu15, removeHLT_Mu7p5_TkXDQMGPUvsCPUstream toHIonandPRefmenusHLT_DoubleMu2_Jpsi_DoubleTkMu0_Phi_v*ToCSCS*single-muon 2018-Parking triggers and datasetIn addition, HLT configs will now use
cms.ConditionalTasks instead ofcms.Tasks thanks a recent update ofConfDB(V03-04-00). Further details on the reasons behind this change can be found in #36938.PR validation:
TSG tests.
If this PR is a backport, please specify the original PR and why you need to backport that PR:
N/A